Release notes

2024r6

Franchises in business API

In this version, the franchise was introduced as an additional content type. Since franchises cannot be

• created or deleted on the Mediagenix Base platform; or

• linked to contracts or transmissions;

the following APIs have been adapted to follow this behaviour.

When the external reference of a franchise is provided as contentId, an error message is returned.

For example, PUT /contracts call:

{
    "statusCode": "404",
    "message": "The specified resource does not exist.",
    "timestamp": "2024-05-31T18:12:55Z",
    "concept": "Contract",
    "id": "8711961000",
    "errors": [
        {
            "errorCode": "CORE-00004",
            "description": "$_Referenced resource not found",
            "data": [
                "9500899926"
            ]
        }
    ]
}

2024r4

Fix for unclear error messages for POST /contracts call in rights API

1)

Previously, when sending a POST /contracts call that included external references of products that did not exist in WHATS'ON, the error message would not clearly show which product was the issue.

{
  "statusCode": "404",
  "message": "The specified resource does not exist.",
  "timestamp": "2024-02-21T10:29:04Z",
    "concept": "Contract",
    "id": "384724",
    "errors": [
        {
            "errorCode": "CORE-00004",
            "description": "$_Referenced resource not found",
            "data": []
        }
    ]
}

This error message has been improved by including the wrong external reference in the data attribute:

{
    "statusCode": "404",
    "message": "The specified resource does not exist.",
    "timestamp": "2024-05-22T07:16:30Z",
    "concept": "Contract",
    "id": "9294339000",
    "errors": [
        {
            "errorCode": "CORE-00004",
            "description": "$_Referenced resource not found",
            "data": [
                "9294345JUY"
            ]
        }
    ]
}

2)

Additionally, when deleting rights using the POST /contracts call that were already linked to a transmission, the error message would not indicate which right this applied to.

{
    "statusCode": "422",
    "message": "Operation cannot be completed due to violations",
    "timestamp": "2024-05-22T07:29:59Z",
    "concept": "Contract",
    "id": "9294339000",
    "errors": [
        {
            "errorCode": "RIGHTS-00007",
            "description": "$_Exploitation right could not be removed",
            "data": []
        }
    ]
}

From this version, this error message includes more information on the right.

{
    "statusCode": "500",
    "message": "HotLink: Unable to delete Broadcast right (External reference: \"9500865058\" - Linear (All linear and on-demand) - 2) because it is used in [PSITxLink] (Field: Exploitation right).",
    "timestamp": "2024-05-23T06:54:47Z"
}

2024r3

Fix for performance of calls with contractType or contractStatus in rights API

Previously, when

• updating a contract with a lot of rights via the POST or PUT /contracts call; and

• the contractType and contractStatus were included in the body but with the same values as before,

the processing of the call would still take a long time. This was because the contract type already triggered an update of the contract status since they are linked, and then the contract status itself was also updated. This happened for every right in the contract, even if the values had not changed.

This issue has been fixed. If the contractType and contractStatus are included in the call body but their values do not change, no updates will be done, which speeds up the call processing.

2024r2

Clearer error message for unknown companies in rights API

Previously, when

• trying to update a reference to a company on a contract or cost definition using the rights API, for example when updating the distributor or creditor attributes; and

• the provided external reference could not be matched to a company,

an unclear error message was returned only mentioning “$_Referenced resource not found” but no additional information.

This issue has been fixed. In this case, the attribute and external reference are now added to the message in the data tag:

{
    "statusCode": "404",
    "message": "The specified resource does not exist.",
    "timestamp": "2024-02-23T15:05:59Z",
    "concept": "Contract",
    "id": "9310771000",
    "errors": [
        {
            "errorCode": "CORE-00004",
            "description": "$_Referenced resource not found",
            "data": [
                "productionCompany not found: 123456"
            ]
        }
    ]
}